<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title>Objective</title>

</head>

<body>
<table border="0" cellspacing="0" cellpadding="0" align="left" width="100%">
  <tr>
    <td width="271" valign="top"><p><a href="./inception.html">Home</a></p></td>
    <td width="271" valign="top"><p align="right"><a href="1.30_vision.html">Next</a></p></td>
  </tr>
</table>
<h1 align="center">Infrastructure Assessment</h1>
<p>The Infrastructure  Assessment is created in the collaboration phase, and documents the accurate  description of the environment and its corresponding variables in which the  solution will reside. The document provides information about all the legacy  systems in place that may affect and/or be accounted for in the solution  design. This is a “living document” as its contents are typically elements that  are constantly under change, thus making the data collection and upkeep a  priority for the team.</p>
<p>An accurate understanding of the current state of the  existing infrastructure increases the probability of successful solution  planning, development, and deployment. Comprehensive information about the  environment, available up front in the project, can facilitate minimizing  changes late in the development stage. This will prevent any significant cost  increases due to re-design or risks. </p>
<h1>Summary</h1>
<p>&lt;&lt;  Provide an overall summary of the contents of this document. Be sure to include  highlights on missing, high risk, or poorly documented sections that require  immediate attention.  Some project  participants may need to know only the highlights of the assessment, and  summarizing creates that user view. It also enables the full reader to know the  essence of the document before they examine the details. &gt;&gt;</p>
<h1>Objectives</h1>
<p>&lt;&lt; The Objectives section describes  the key objectives of the infrastructure assessment process.  Identifying  the objectives signals that the assessment process has occurred within  strategic parameters established before the assessment began. &gt;&gt;</p>
<h1>Project Scope </h1>
<p>&lt;&lt; The  Project Scope section is a restatement of the project’s scope with a specific  slant toward how it relates to the current infrastructure. For example, if a  complete network design is considered out of scope, but the current state  assessment finds areas where the current network design will affect the  solution, then restate the scope to set expectations. &gt;&gt;</p>
<h1>Recommendation</h1>
<p>&lt;&lt; Recommendation section identifies  any data from the assessment elements collected so far that may cause specific  implications to the proposed solution. It should also suggest possible ways to  resolve those issues.  This information may significantly impact the  project and should be documented and transmitted formally. &gt;&gt;</p>
<h1>Technology  Architecture</h1>
<p>            &lt;&lt; The Technology Architecture  section provides details on the following architecture items to the appropriate  level that enables the team to make appropriate solution design decisions.  Include any graphs or maps useful for these areas. &gt;&gt;</p>
<h2>Network Architectures</h2>
<p>&lt;&lt;  Begin text here &gt;&gt;</p>
<h2>Windows Domain  Architectures</h2>
<p>&lt;&lt;Begin  text here&gt;&gt;</p>
<h2>Windows Security</h2>
<p>&lt;&lt;Begin  text here&gt;&gt;</p>
<h2>Network Infrastructure  Services</h2>
<p>&lt;&lt;Begin text here&gt;&gt;</p>
<h2>Information Infrastructure and Services</h2>
<p>&lt;&lt;Begin text here&gt;&gt;</p>
<p>&nbsp;</p>
</body>
</html>
